closes #1285

Having both of these method is ambiguous. I have made it so only get is the real method, and get_values is its alias.

def get_values(self, *args, **kwargs) -> ValueRange:
        """Alias for :meth:`~gspread.worksheet.Worksheet.get`"""
        return self.get(*args, **kwargs)

Potential problems:

• get_values used to return type List[List[str]].
  get returns a ValueRange
  thus now get_values returns a ValueRange instead
  ValueRange subclasses list, so it's okay?

I agree about the duplicate method.

about the linting: I think we can solve it using the propose changes in the code.

Changing the outcome of the test is good sing of a breaking change 😮 .

Yes, good that this is 6.0.0 ;). Do you think the breaking change is too big?

about the linting: I think we can solve it using the propose changes in the code.

Not sure what you mean by "linting"

Changing the outcome of the test is good sing of a breaking change 😮 .

Yes, good that this is 6.0.0 ;). Do you think the breaking change is too big?

not too big, just may be it's too many. I don't know, I feel like this is a lot of changes.

about the linting: I think we can solve it using the propose changes in the code.

Not sure what you mean by "linting"

I meant typing sorry 🙊 but you solved it by applying the proposed code change

Yes, this is a big change. It needs some thinking about.

The alternate options are:

• leave get as-is, and make get_values be identical (alias) apart from it pads values. The names don't really make sense why this is the case, though.
• try and make sure the API of get and get_values always remains the same

For maximum compatibility, get_values should be an alias of get, but return type List[List[str]].

I propose the breaking change here that:

• get does start padding values

Then, the only difference between get and get_values is the return type (List[List[str]] vs ValueRange)

I propose the breaking change here that:

• get does start padding values

I agree with this change, but the default behavior must stay so:

• get can pad the values
• when get is called by default it does not pad the values
• when get_values calls get it requests it to pad the` values.

this way we keep the same behavior as before but we allow user to padd at both levels. Then we'll be able to deprecate the old behavior in the next+2 major release if we want to

Then, the only difference between get and get_values is the return type (List[List[str]] vs ValueRange)

can we add some flags again to offer the choice of the returned value ? default: keep the old return type, flag is set: return ValueRange ?

*I'm sorry I edited your comment instead of replying ! 🤦 *

We are waiting for #1305 to be merged into feature/release_6_0_0 branch. Thus we are waiting for #1320.

This is now ready to merge. Technically, this introduces no changes to the public API (👻wooo👻)

I have removed all code from worksheet.get_values so it is now simply

All heavy lifting is now done in the worksheet.get function.

You may notice that worksheet.get now has two very similar kwargs: pad_values and maintain_size. To see what the difference is, please see the readme

pad_values is introduced to differentiate the behaviour of get and get_values (see top of thread).

maintain_size is the new feature added by #1305

They cannot be combined into one kwarg for two reasons:

• this would be a breaking change (we could do it here since this is for 6.0.0)
• it would not be possible for indeteminate size ranges
  this is to say that pad_values operates on all arrays, just making them rectangular. maintain_size must know the size to pad the array to. Thus, you cannot use maintain_size for a call to "A:C", etc.

added #1303 into this PR...